|
|
|
|
|
|
|
This represents on-the-fly design (OTFD) by compromise; there is no program architecture on which this compromise is based. Without some organized methodology for the programming process, one person's spaghetti coding style can take precedence over that of the other programmer. This is especially damaging when the other programmer is timid and nonconfrontational (a prevalent behavior in the programming community). More often than not, one of these programmers usually quits or in some way is removed from the project when things go wrong (and with OTFP, they often do). |
|
|
|
|
|
|
|
|
In some cases, it gives the project manager a false sense of security. For some curious reason, some project management styles tend to prefer one state of the project life cycle in the absence of all others: programming. Seldom is serious treatment given to analysis and design, much less to a formal methodology for the programming process as well as to the formulation of an architecture for the program. |
|
|
|
|
|
|
|
|
OOP, and the entire object-oriented process, provides greater and longer lasting benefits to every project stakeholder (programmer, manager, end user, and so on). As mentioned earlier, one chief benefit of OOP is that it facilitates better team development. This is important for users of Visual Basic. Visual Basic offers enough features to enable with ease the implementation of object technology and formal object-oriented analysis and design methodologies. Team development is also easier in Visual Basic and facilitates the creation of projects that incorporate the individual talents of each developer. Visual Basic's support of an object repository (MS Repository) adds a good framework for team development as well. A Visual Basic project, in any size of corporate enterprise, also reflects the competence of its team members. In this context, a project represents a group of people who have as a common goal the development of an application or suite of applications to carry out some business process. |
|
|
|
|
|
|
|
|
Another way that OOP lends itself well to project team development is by supporting the ability to break down a complex system into simpler abstractions (or understandable portions). Each abstraction, then, can be more easily assigned to team members for better definition and construction (application design and programming). Without an OOP background, novices in Visual Basic tend to revert to traditional waterfall techniques (or similar) as soon as the first problem in the project emerges. This chapter helps you avoid these mistakes by helping you to embrace OOP. |
|
|
|
|
|